Repository navigation
Move ASan CI job to reusable-san.yml - #159367
Conversation
This refactors the CI configuration for ASan to deduplicate some logic, and bring it together with the other sanitzers. As a sideeffect, it will also run `--with-pydebug` and build with the Clang compiler.
|
If there are no objections, I'll merge this in a few days. |
|
This switches from Is this intentional or okay to skip under ASan? |
They are skipped anyway (tests involving libX11 can segfault on ASan builds), see this run for example. As for the other resources, most of them are network related (since we exclude |
|
To be honest, I feel like it's not worth the additional complexity. Currently, people can easily add or remove themselves, and they also have the option to be as specific as they'd like. LLVM does this to an extent, and it's a bit of pain to wait for an administrator to add or remove you from a team (and, you also have less control over what you're subscribing to). |
|
true! im not fussed about it either way :D |
|
Considering we now have Dependabot configured to create PRs against each branch individually, do we need to bother backporting all the way? |
|
Thanks @StanFromIreland for the PR 🌮🎉.. I'm working now to backport this PR to: 3.14, 3.15. |
|
Sorry, @StanFromIreland, I could not cleanly backport this to Please backport manually with cherry_picker, see the devguide for more information. |
|
Sorry, @StanFromIreland, I could not cleanly backport this to Please backport manually with cherry_picker, see the devguide for more information. |

This refactors the CI configuration for ASan to deduplicate some logic, and bring it together with the other sanitzers.
As a sideeffect, it will also run
--with-pydebugand build with the Clang compiler.